Mobile device and control method thereof

ABSTRACT

A mobile device is provided. The mobile device includes a display unit, a sensor configured to sense user&#39;s touch done on a surface of the display unit in a disabled state of the display unit, a storage unit configured to store preset gesture information, a controller configured to enable the display unit when a user&#39;s touch operation matched with the gesture information is sensed, execute a wallet application, and display an execution screen, and a communication unit configured to transmit information for a selected payment option to an external apparatus when the payment option is selected on the execution screen and perform a payment. The payment is simply done.

CROSS-REFERENCE TO RELATED APPLICATION

This is a Continuation of application Ser. No. 15/332,544 filed Oct. 24,2016, which is a continuation application of Ser. No. 13/915,173 filedJun. 11, 2013 and issued as U.S. Pat. No. 9,483,758, which claimspriority from U.S. Provisional Patent Application No. 61/658,156, filedon Jun. 11, 2012, in the United States Patent and Trademark Office andKorean Patent Application No. 10-2013-0001779, filed on Jan. 7, 2013, inthe Korean Intellectual Property Office, the disclosures of which areincorporated herein by reference in their entireties.

BACKGROUND 1. Field

Apparatuses and methods consistent with exemplary embodiments relate toa mobile device and a control method thereof, and more particularly, toa mobile device capable of controlling an operation thereof according toa user's gesture and a control method thereof.

2. Description of the Related Art

With development of electronic technology, various types of userterminal apparatuses have been used. In particular, recently, spread ofhigh-spec user terminal apparatuses such as smart phones or tabletpersonal computers (PCs) are greatly increased.

Thus, a type of serve supported by the user terminal apparatusesgradually highly qualified. In particular, the users tend to preferfaster, more convenient, and simpler service as compared in the past. Byconsidering these circumstances, research on services providable fromthe user terminal apparatuses have consistently progressed in variousways.

There is shopping service among the services. That is, in the past, theusers purchase goods off-line only using cash or a credit card. Inrecent years, the users shop using a method of ordering goods in on-lineshopping malls and paying a transaction amount by credit card, mobilephone authorization, deposit without a bankbook, and the like, using ausers' own PCs.

However, it is cumbersome in the shopping service in that the useralways has to use the credit for a payment. That is, the current userterminal apparatuses support shopping services in the limited level.

Therefore, there is a need for technology capable of providing theshopping services in the users-portable mobile devices.

However, to execute applications required to perform the payment in themobile devices, it is inconvenient to perform operations several times.Therefore, it is difficult to enable the shopping using the mobiledevices.

SUMMARY

One or more exemplary embodiments may overcome the above disadvantagesand other disadvantages not described above. However, it is understoodthat one or more exemplary embodiment are not required to overcome thedisadvantages described above, and may not overcome any of the problemsdescribed above.

One or more exemplary embodiments are to provide a mobile device capableof conveniently simply providing shopping service according to a user'soperation and a control method thereof.

According to an aspect of an exemplary embodiment, there is provided amobile device. The mobile device may include: a display unit; a sensorconfigured to sense user' touch done on a surface of the display unit ina disabled state of the display unit; a storage unit configured to storepreset gesture information; a controller configured to enable thedisplay unit when a user' touch operation matched with the gestureinformation is sensed, execute a wallet application, and display anexecution screen; and a communication unit configured to transmitinformation for a selected payment option to an external apparatus whenthe payment option is selected on the execution screen and perform apayment.

In other exemplary embodiments, the mobile device may further include afingerprint sensor configured to sense a fingerprint. The controller mayenable the display unit and execute the wallet application when theuser' touch operation matched with the gesture information and a user'sfingerprint matched with pre-registered fingerprint information aresensed.

The disabled state of the display unit may be a state in which thedisplay unit is off or a locked screen is displayed.

The user's touch operation may be a gesture in which a plurality ofpoints are touched on the surface of the display unit and move toincrease a distance therebetween.

According to another aspect of an exemplary embodiment, there isprovided a payment method of a mobile device. The payment method mayinclude: sensing user's touch done on a surface of a display unit of themobile device in a disabled state of the display unit; enabling thedisplay unit when a user's touch operation matched with preset gestureinformation is sensed, executing a wallet application, and display anexecution screen; and transmitting information for a selected paymentoption to an external apparatus when the payment option is selected onthe execution screen and performing a payment.

In another exemplary embodiment, the payment method may further includesensing a fingerprint; and determining whether or not the sensedfingerprint is matched with pre-registered fingerprint information. Thewallet application may be executed when the user's touch operationmatched with the gesture information and a user's fingerprint matchedwith the fingerprint information are sensed.

The disabled state of the display unit may be a state in which thedisplay unit is off or a locked screen is displayed.

The user's touch operation may be a gesture in which a plurality ofpoints are touched on the surface of the display unit and move toincrease a distance therebetween.

According to the above-described exemplary embodiments, shoppingservices using mobile devices may be simply conveniently performed.

In yet another exemplary embodiment, there is a smartphone including: atouchscreen configured to receive finger input; a memory configured tostore a plurality of gesture information; a controller configured tocompare the received finger input with the plurality of gestureinformation and, if the received finger input corresponds to one gestureinformation of the plurality of gesture information, to perform at leastone from among turning on the smartphone, waking up the smartphone, orunlocking the touchscreen, to execute a payment applicationcorresponding to the one gesture information of the plurality of gestureinformation, and to display a screen of the executed paymentapplication; and a wireless communication unit configured to wirelesslytransmit information regarding a payment command received through thepayment screen.

In one exemplary embodiment, the controller is configured toautomatically execute the payment application after turning on thesmartphone, waking up the smartphone or unlocking the touchscreen of thesmartphone.

In another exemplary embodiment, the received finger input is an inputreceived at the touchscreen by detecting a physical contact between afinger and the touchscreen.

In yet another exemplary embodiment, the received finger input is aninput received at the touchscreen by detecting a finger hovering overthe touchscreen.

Additional aspects and advantages of the exemplary embodiments will beset forth in the detailed description, will be obvious from the detaileddescription, or may be learned by practicing the exemplary embodiments.

BRIEF DESCRIPTION OF THE DRAWING FIGURES

The above and/or other aspects will be more apparent by describing indetail exemplary embodiments, with reference to the accompanyingdrawings, in which:

FIG. 1 is a block diagram illustrating a configuration of a mobiledevice according to an exemplary embodiment;

FIG. 2 is a flowchart illustrating a control method of a mobile deviceaccording to an exemplary embodiment;

FIG. 3 is a view illustrating an example of a user' operation forimmediately executing a wallet application in a mobile device;

FIG. 4 is a view illustrating an example of an information systemmanaged by a wallet application;

FIG. 5 is a view illustrating an example of a main execution screen of awallet application;

FIGS. 6 and 7 are views illustrating examples of card list screens;

FIG. 8 is a view illustrating a process of performing a payment througha card list screen;

FIG. 9 is a view illustrating a screen specifically displaying a creditcard list;

FIG. 10 is a view illustrating a screen specifically displaying anidentifier (ID) card list;

FIG. 11 is a view illustrating a screen specifically displaying a pointcard list;

FIG. 12 is a view illustrating an example of a payment screen;

FIGS. 13 and 14 are views illustrating examples of payment authorizationscreens;

FIG. 15 is a view illustrating an example of a receipt list screen;

FIG. 16 is a view illustrating an example of an electronic receipt;

FIG. 17 is a view illustrating an example of a wish list;

FIG. 18 is a view illustrating an example of a path guide screen;

FIG. 19 is a view illustrating a process of executing a walletapplication by a user' touch operation and displaying an executionscreen of the wallet application;

FIG. 20 is a view illustrating a process of executing a walletapplication on a home screen by icon selection;

FIG. 21 a view illustrating an example of a setting screen of a walletapplication;

FIG. 22 is a flowchart specifically illustrating a control method of amobile device according to another exemplary embodiment;

FIG. 23 is a view illustrating a payment process of a mobile deviceaccording to another exemplary embodiment;

FIG. 24 is a view illustrating an example of an error message displayedwhen an incorrect passcode is entered;

FIG. 25 is a view illustrating an example of a payment completionmessage;

FIGS. 26 and 27 are view illustrating a control method of a mobiledevice according to other exemplary embodiments:

FIG. 28 is a view illustrating a method of recognizing a user'sfingerprint;

FIG. 29 is a block diagram integrally illustrating a configuration of amobile device according to various exemplary embodiments; and

FIG. 30 is a view illustrating a software configuration of a mobiledevice according to an exemplary embodiment.

DETAILED DESCRIPTION OF THE EXEMPLARY EMBODIMENTS

Hereinafter, exemplary embodiments will be described in more detail withreference to the accompanying drawings.

In the following description, same reference numerals are used for thesame elements when they are depicted in different drawings. The mattersdefined in the description, such as detailed construction and elements,are provided to assist in a comprehensive understanding of the exemplaryembodiments. Thus, it is apparent that the exemplary embodiments can becarried out without those specifically defined matters. Also, functionsor elements known in the related art are not described in detail sincethey would obscure the exemplary embodiments with unnecessary detail.

FIG. 1 is a block diagram illustrating a configuration of a mobiledevice according to an exemplary embodiment. The mobile device may bevarious types of apparatuses such as a mobile phone, a tablet PC, anelectronic book, a personal digital assistant (PDA), an MPEG-1 audiolayer 3 (MP3) player, and a laptop PC.

Referring to FIG. 1, the mobile device includes a display unit 110,e.g., display, a sensor 120, a controller 130, and a storage unit 140,e.g., storage.

The display unit 110 may be implemented with various types of displayssuch as a liquid crystal display (LCD), an organic light emitting diode(OLED) display, or a plasma display panel (PDP). A driving circuit whichmay be implemented with an amorphous (a-Si) thin film transistor (TFT),a low temperature polysilicon (LTPS) TFT, an organic TFT (OTFT), or thelike, and a backlight unit, and the like are further included in thedisplay unit.

The sensor 120 may sense user' touch done on a surface of the displayunit 110. The sensor 120 may be implemented with various types of touchsensors such as a capacitive type touch sensor, a resistive type touchsensor, or a piezoelectric type touch sensor. The capacitive touchsensor is configured to sense microelectricity excited to a user's bodyusing a dielectric coated on a surface of the display unit when a partof the user's body is touched on the surface of the display unit110, andcalculate a touch coordinate. The resistive type touch sensor is aconfigured to include two electrode plates built in the display unit110, sense current through the upper and lower electrode plates incontact with each other at a touched point when the user touches ascreen, and calculate a touch coordinate. Thus, the sensor 120 may sensevarious types of user's touch operations such as touch, touch and drag,flick, long tough, and double touch and various types of user operationssuch as a motion gesture, a motion gesture, and speech input.

The sensor 120 may sense the user touch in a disabled state of thedisplay unit 110. The disabled state of the display unit 110 includes astate in which the display unit 110 displays a lock screen as well as astate in which the display unit 110 is off and a state in which themobile device is in a sleep state. That is, the mobile device 100automatically enters a lock state to turn off the display unit 110 whenthe user does not use the mobile device for above a certain period oftime. In the screen off state, when a hardware button provided in a bodyof the mobile device is selected, the display unit displays a lockscreen. When the user operation for performing an unlock operation onthe lock screen, the mobile device releases the lock state and displaysa main screen.

The controller 130 enables the sensor 120 to be consistently maintainedin an enable state so that the sensor senses the user touch on a surfaceof the display unit 110 even in the disabled state of the display unit110.

The storage unit 140 stores operating system (OS) for driving the mobiledevice, programs, data, and various kinds of contents. Preset gestureinformation is included in the data stored in the storage unit 140.

When the user touch is sensed by the sensor 120, the controller 130determines whether or not the user touch operation matches the gestureinformation stored in the storage unit 140. When it is determined thatthe user touch operation matches the gesture information, the controller130 enables the display unit 110, automatically executes an applicationcorresponding to the user touch operation, and immediately displays anexecution screen of the application. The application corresponding tothe user touch operation may be set by the intention of the designer orthe user. In the exemplary embodiment, an example in which a walletapplication, which is capable of providing shopping service such as apayment and purchase history management, matches the user touchoperation is illustrated. That is, the controller 130 immediatelydisplays the execution screen of the wallet application when a specificuser touch operation is input even in the disabled state of the displayunit 110.

The communication unit 150 is configured to perform communication withan external apparatus. The communication unit 150 may perform thecommunication with the external apparatus using at least one of variouscommunication methods such as a wireless local area network (LAN),wireless fidelity (Wi-Fi), Bluetooth, Zigbee, near field communication(NFC), and the like.

With regard to shopping service, the communication unit 150 may performcommunication with external apparatuses, for example, server apparatusessuch as servers of operators operating various online shopping mallsites, portal site servers, or cloud servers, and servers of serviceproviders providing point of sale system (PoS) or other payment gateway(PG) service.

As one example, assuming that the communication unit 150 performscommunication with the PoS, when the user selects one payment option onan execution screen of a wallet application and then inputs a paymentcommand, the communication unit 150 transmits information for theselected payment option to the PoS and performs a payment. At this time,a short-range wireless communication method such as NFC may be used.That is, when the communication unit 150 includes an NFC module, theinformation for the payment option may be transmitted by NFC tagging tothe PoS. The NFC tagging means a behavior which approaches and touchesthe external apparatus (that is, PoS and the like) within a distancerange which can perform short-range wireless communication.

FIG. 2 is a flowchart specifically illustrating a payment methodperformed in the mobile device of FIG. 1. Referring to FIG. 2, when theuser touch is sensed (S210), the controller 130 determines whether ornot the sensed touch content matches preset gesture information (S220).The gesture information means information in which various items, forexample, a location of a first touch point, the number of touch points,change in the touch point, change in a direction, trajectory, speed,etc., are combined.

The controller 130 enables the display unit (S230) when it is determinedthat the sensed touch content matches the gesture information, executesa wallet application, and immediately displays an execution screen ofthe wallet application (S240). When the user's next operation isperformed on the execution screen, the payment is performed according tothe user's next operation (S250). When a payment option set to defaultexists on the execution screen of the wallet application, the paymentmay be directly done only through a simple operation such as NFC taggingor button selection without a separate process of selecting a paymentoption on the execution screen.

According to the above-described exemplary embodiment, the payment isperformed only through simple one or two operations of the user evenwhen the mobile device is in a lock state, so that shopping service maybe conveniently used.

FIG. 3 is a view illustrating an example of a user's operation forexecuting a wallet application. In FIG. 3, 3000 a illustrates that adisplay unit 110 is in an off state, that is, in a screen off state, orillustrates that the mobile device is in a sleep state. In this state,the user gestures to touch two points T1 and T2 on a surface of thedisplay unit 110 using two fingers and then to spread the two fingers atboth sides, the controller 130 performs an unlock operation, immediatelyexecutes the wallet application, and displays an execution screen 320 asillustrated in 3000 b.

In FIG. 3, 3000 c illustrates that the display unit 110 displays a lockscreen 310. When the user performs a preset first user operation on thelock screen 310, unlock is done, and thus a home screen may bedisplayed. On the other hand, when the user performs a preset seconduser operation on the lock screen 310, the unlocking is done, and thusthe execution screen 320 of the wallet application may be immediatelydisplayed. Here, the second user operation may gesture that the usertouches the two points T1 and T2 and spreads a gap between the twopoints.

As the gesture information in the exemplary embodiment of FIG. 3,coordinate ranges of the points T1 and T2 at which first touch is done,a trajectory and direction of changes in touch points after the firsttouch, and the like have been preset and stored in the storage unit 140.Thus, when the gesture information has been strictly set, execution ofthe wallet application due to the user's unintended touch may beprevented in the mobile device 100.

The wallet application may manage various pieces of information relatedto the shopping service. The shopping service may be largely dividedinto a process of searching and selecting goods, a process ofpurchasing, and a process of managing after the process of purchasing.

The good search and selection may be performed both on-line andoff-line. Specifically, the controller 130 may execute web browser,access to Internet, and display a site screen provided from variousonline shopping malls. The user searches for and selects his/her desiredgoods while the user views the site screen. Additional service such as awish list may be provided in the selecting process. That is, the userhas stored the goods, which are not immediately purchased but intendedto purchase, in the wish list and then determines to purchase later. Onthe other hand, the process of searching for and selecting goods may bedone off-line. Specifically, the user directly looks at and chooses thegoods in department stores or shops.

When the process of searching for and selecting the goods is performedas described above, the purchase of the goods, that is, a payment may bedone through the mobile device. Specifically, the mobile device 100 mayperform the payment using the wallet application. In the walletapplication, the payment may be performed using information for variouspayment options such as a credit card, an identifier (ID) card, a pointcard, a coupon, and an event card which are possessed by the user. Thespecific payment method using the wallet application will be describedin more detail later.

After the purchase of the goods is done, the user may receive anelectronic receipt or bill and manage a purchasing history. Thus, thewallet application may recognize purchase propensity of the user torecommend appropriate goods, purchase time, a purchase place, and thelike, and further recognize problems and advice for the user to refrainfrom indiscreet purchase.

To provide various shopping services, the wallet application may storeand manage various pieces of information related to shopping.

FIG. 4 illustrates an example of an information system managed by awallet application.

-   Referring to FIG. 4, a wallet application 400 may be divided into a    payment part 410 configured to be in charge of an amount payment and    a shopping management part 420. Information such as a card list 411,    a payment mode 412, and bills 413 is managed in the payment part 410    and information such as wishes 421 and a shop path 422 is managed in    the shopping management part 420.

The card list 411 includes card information such as credit cardinformation 411-1, ID card information 411-2, point card/stampinformation 411-3, and instant card information 411-4 and the paymentmode 412 includes mode information such as an automatic mode 412-1 and amanual mode 412-2. In addition, the bills information 413 includesinformation such as a bill 413-1, a split 413-2, and a budget 413-3. Thewishes information 421 includes information such as wish items 421-1, awish place 421-2, and a coupon 421-3 and the shop path information 422includes information such as a map 422-1 and an item list 422-2.

The controller 130 may execute the wallet application 400 to manage anduse various pieces of information as illustrated in FIG. 4. Hereinafter,various user interface screens displayed in the display unit 110according to the execution of the wallet application and a method ofusing the same will be described in detail.

FIG. 5 illustrates an example of a home screen 500 of a walletapplication. Credit card information 510, ID card information 520,payment detailed and predicted information 530, shopping guideinformation 540, menus 501, 502, and 503, and the like are displayed inthe home screen 500.

The credit card information 510 indicates information for a credit cardmost frequently used or set to default. A card company, a card name, atotal amount used this month, specified limit, a total amount used lastmonth, and the like may be displayed together with the information forthe credit card in the credit card information 510. Further, a paybutton 511 configured to immediately perform a payment using thecorresponding credit card may be displayed at one side of the creditcard information 510.

The ID card information 520 may display information for a basic ID cardissued by institutions such as a company or a school. Absenteeism andtardiness and admittance relevant records, and the like may be alsodisplayed in the ID card information 520.

An amount used this month, an estimated amount to be spent, a guidemessage, and the like may be displayed in the payment detailed andpredicted information 530. The guide message may be displayed in variouscontents according to a case in which expected spending and a budget arebalanced, a case in which spending for a specific category is large, acase in which the expected spending is larger than the budget, a case inwhich the expected spending is smaller than the budget, and the like.

The shopping guide information 540 is divided into a plurality of tabbedpages. FIG. 5 illustrates a state in which the shopping guideinformation 540 is divided into tabbed pages such as shopping tips andrecent bills. Information for recommending shopping to the user isdisplayed in the shipping tips. The ‘shopping tips’ may be displayedwhen an item, which satisfies a condition such as a schedule, time, apurchasing pattern, and a current location, exists among itemsregistered in the wish list generated by the user. Information relatedto a split payment requested by a friend, contents for split paymentrequest, recent receipts of purchase, and the like may be displayed inthe ‘current bills’. When the ‘recent bills’ is selected, a detailedview screen for social network service (SNS) or e-mail requesting thespilt payment and an electronic receipt, and the like may be displayed.

In addition, as illustrated in FIG. 5, in the menu region, a home menu501 for shortcut to a payment home screen, a card list menu 502 forshortcut to a screen providing various cards relevant information, thebills menu 503 for providing information relevant to a list of purchaserecords of the user and spending, and the like may be displayed.Although not shown, in the menu region, a wishes menu for displaying alist in which information for goods or shops interestedon-line/off-line, or coupon/discount information is collected or a‘shopping path’ menu for displaying a path on a map by automaticallygrouping the closest path among items registered in the wishes list orby grouping items selected by the user may be further displayed.

FIG. 6 illustrates an example of a card list screen displayed when thecard list menu 502 is selected in the payment home screen 500. Referringto FIG. 6, a credit card item 611, an ID card item 621, a point carditem 631, a ticket item 641, and the like are displayed in the card listscreen 600. Information 610, 620, 630, and 640 for one representativecard is displayed in each item. The menu area 501, 502, and 503illustrated in FIG. 5 are kept the same in FIG. 6.

The number (for example, 10) of registered credit cards is displayed inthe credit card item 611. When the credit card item 611 is selected,lists for all stored cards may be displayed. The lists will be describedlater. Further, a pay button 612 may be displayed in the credit carditem 611. The pay button 612 is a button configured to immediatelyperform a payment using a credit card displayed in the card information610. When the user presses the pay button 612, the controller 130progresses a payment process using the displayed credit card.Specifically, the detailed payment process will be described in moredetail later.

The ID card item 621 may be displayed in the same manner as the creditcard item 611. That is, information 620 for one representative card maybe also displayed.

The point card item 631 is an item for displaying loyalty cards such asvarious types of point cards, mileage cards, and stamps. The ticket item641 is an item for displaying information of cards for one-time use suchas a ticket, a parking ticket and a gift card.

FIGS. 5 and 6 have illustrated the examples of screens implemented inproducts in which a height length of a display is larger than a widthlength thereof, such as a mobile phone, but may be applied to a mobiledevice including a display in which a width length is larger than aheight length, such as tablet personal computers (PCs).

FIG. 7 illustrates a layout of a card list screen 600 in which a widthlength is larger than a height length. Referring to FIG. 7, an image 651of a representative card and information 652 for the representative cardmay be displayed in the card list screen 600 together with card items611, 621, 631, and 641 and card information 610, 620, 630, and 640.Therefore, a payment using the representative card may be immediatelydone in the card list screen 600 without a process of selecting aseparate payment option again.

When the mobile device may sense a rotation state thereof, if the mobiledevice 100 is rotated 90 degrees to the left or to the right whiledisplaying the card list screen as illustrated in FIG. 6, the screen isconverted into the layout as illustrated in FIG. 7.

FIG. 8 illustrates an example of a process of performing a paymentthrough card selection. 8000 a illustrates the card list screen 600.When the user touches (T) the card information 610 in the card listscreen 600, the detailed information screen 700 for a selected card,that is, a representative card is displayed as illustrated in 8000 b. Afront image 710 of the card, card benefit information 720, selectionmenus 730 and 740, and the like may be displayed in the detailedinformation screen 700. A bar code 721 including card information, andthe like may be displayed in the card benefit information 720. Thus, thepayment may be performed using the mobile device in a PoS including abar code reader.

When the user selects the pay menu 740 in the detailed informationscreen 700, the detailed information screen 700 is converted into apersonal identification number (PIN) input screen 800 as illustrated in8000 c. An input region 810, a key pad 820, selection menus 830 and 840,and the like may be displayed in the PIN input screen 800. When the userinputs a correct passcode through the key pad 820, the mobile devicetransmits payment information to the external apparatus and performs thepayment.

When the items 611, 621, 631, and 641 are selected on the card listscreen, the lists for the cards registered in the corresponding itemsmay be displayed.

FIG. 9 illustrates an example of screen conversion when an item isselected on the card list screen. When the credit card item 611 isselected in the card list screen 600 as illustrated in 9000 a, thecontroller 130 displays a credit card list 900 using information for thecredit cards of the user registered in the storage unit 140 or anexternal server apparatus as illustrated in 9000 b. Various pieces ofcard information 910 to 970 and pay buttons 911 to 971 for therespective cards are displayed in the list 900. Only the pay buttons 911to 971 for the credit cards may be displayed.

When a portion of the credit card item 611 is touched (T) in the list900, the controller 130 may convert the credit card screen 900 into thescreen as illustrated in 9000 a again and display the converted screen.When the user uses other credit cards other than the credit cards mostfrequently used, the user may select the payment option in a state inwhich the list is displayed as illustrated in 9000 b. In the top of thelist as illustrated in 9000 b, a card designated to a default card bythe user or most frequently used, that is, a representative card isdisplayed. The user may perform long tapping or touching and dragging onone card on the list 900 to change a location of the card or to deletethe card from the list 900. Further, when a large number of cards whichmay not be displayed in one screen are registered, the user may performscrolling on the card list screen in a vertical direction.

FIG. 10 illustrates an example in which an ID card is selected. When theID card information 620 displayed below the ID card item 621 in 10000 ais selected, the controller 130 displays a detailed information screen1000 for the selected ID card. An ID card image 1010, detailedinformation 1020 including a bar code and the like, an OK button 1030,and the like may be displayed in the detailed information screen 1000.When the OK button is selected, the screen 1000 may be converted intothe screen as illustrated in 10000 b.

FIG. 11 illustrates an example in which a point card is selected. Whenthe point card information 630 is selected in 11000 a, the controller130 displays detailed information screen 1100 for a representative pointcard as illustrated in 11000 b. A representative point card image 1110,detailed information 1120, selection menus 1130 and 1140, and the likeare displayed in the detailed information screen 1100. When a use itmenu 1140 of the selection menus is selected, the controller 130 appliesbenefits of the corresponding point card and performs a payment process.For example, when a free coupon or a discount coupon is used, thepayment for an amount reduced by the amount stated in the coupon isprogressed. 11000 c illustrates an example that the point card isapplied. When the use it menu is selected in the detailed informationscreen 1100, a mark 1150 indicating that the coupon has been used isdisplayed in the card image 1110 and a mark such as the bar code isdeleted from the detailed information 1120 not to be used any longer.The selection menu is changed to an OK button 1160. When the userselects the OK button 1160 or when a preset period of time (for example,5 seconds) is elapsed, the controller 130 displays the card list screen600 as illustrated in 11000 a again. When the representative point cardhas been used, a point card at a top among the unused point cards may bedisposed in the point card information 630 of the card list screen 600.

Even when the ticket information 640 is selected, the payment isprocessed in a similar manner to the point card and thus illustrationand description thereof will be omitted.

Various examples of selecting a payment option have been described.Hereinafter, various examples for a method of proceeding the paymentwill be described in more detail.

In the state in which the wallet application is automatically executed,the user performs tagging on a host apparatus such as a PoS terminal oraccess to the host apparatus in a wireless communication manner toproceed the payment. When information for an amount to be paid istransmitted from the PoS terminal by the tagging or wirelesscommunication, the controller 130 executes the wallet application toimmediately display a payment screen in which the payment amount isdisplayed. When the pay button in the screen as illustrated in FIG. 6 or9 is selected, the controller 130 may display the payment screentogether with the information for the selected credit card. FIG. 12illustrates an example of the payment screen in which the payment amountis displayed.

Referring to FIG. 12, headline information 1210, various kinds of cardinformation 1220 and 1230, selection menus 1240 and 1250, and the likemay displayed in a payment screen 1200.

Information 1211 for the selected credit card, an icon 1212 for changinga card, information such as a requested payment amount 1213, and thelike may be displayed in the headline information 1210. A credit cardimage 1220, a coupon image 1230, and the like may be included in thecard information. The credit card image 1220 may be an imagecorresponding to the credit card displayed in the headline information1210. Icons 1221, 1222, 1231, and 1232 for conversion into another cardand the like may be displayed at both sides of each of the images 1220and 1230.

A credit card, coupon, point card or the like initially displayed in thepayment screen as illustrated in FIG. 12 may be automatically selectedand recommended by the controller 130. That is, by considering a paymentdetail and a payment time of the user, a shop requesting the payment, anitem to be paid, and the like, a card which may provide the greatestbenefit, a card having the largest remaining credit limit, a card inwhich the user's preference is highest, or the like may be selected. Thecontroller 130 may display the selected card at the top of the list as arepresentative card. Even in the case of a coupon, the controller 130may select and display the coupon in the similar manner to theabove-described method. When a plurality of coupons are searched, thecontroller 130 may change the benefits of the coupons to amounts andrecommend a coupon which provides the greatest benefit or recommend acoupon having the smallest remaining expiration data.

When the user selects an OK menu 1250 in the screen as illustrated inFIG. 12, the screen 1200 may be converted into an authorization screenfor payment. The authorization screen may be implemented with a PINinput screen as illustrated in FIG. 8, but the authorization screen isnot limited thereto. That is, various authorization screens may beprovided according to setting of the user.

FIGS. 13 and 14 illustrate various examples of authorization screens.

Referring to FIG. 13, information 1310 for an amount to be paid, aninput region 1320 to which the user's signature is input, selectionmenus 1330 and 1340, and the like may be displayed in an authorizationscreen 1300. When the user selects an encryption type as a signature ina setting screen, the authorization screen 1300 as illustrated in FIG.13 may be provided.

FIG. 14 illustrates another example of an authorization screen.Referring to FIG. 14, information 1410 for an amount to be paid, apattern input region 1420 to which the user inputs a pattern, selectionmenus 1430 and 1440, and the like may be displayed in an authorizationscreen 1400. When the user selects an encryption type as a pattern inthe setting screen, the authorization screen 1400 as illustrated in FIG.14 may be provided.

In addition, the wallet application may generate the screen usinginformation for a transaction statement or an electronic receipt.

FIG. 15 illustrates an example of a list screen for an electronicreceipt. Referring to FIG. 15, details 1510, 1520, and 1530 paid usingan electronic application are arranged and displayed in a list form in alist screen 1500. The list screen as illustrated in FIG. 15 may bedisplayed when the bills menu 503 is selected in the payment home screen500 as illustrated in FIG. 5 or other screens.

FIG. 16 illustrates a screen when one electronic receipt is selected inan electronic receipt list screen. Referring to FIG. 16, when oneelectronic receipt is selected, a detailed information screen 1600 forthe selected receipt is displayed. Specifically, a payment amount, acompany name, a payment data, purchase detail, and selection menus 1610and 1620 are displayed. Among the selection menus, a split menu 1610 isa menu for requesting payment exclusive charge or payment sharing toother users based on the payment amount and an OK menu 1620 is a menufor terminating the wallet application after the receipt is stored. Inaddition, a share menu for sharing the payment detail, a list menu forviewing a receipt list, and the like may be further displayed.

FIG. 17 illustrates an example of a wish list generated by the user. Thewallet application as illustrated in FIG. 3 may also manage informationfor the wish list. The wish list is a list in which the user hasregistered interested goods. Referring to FIG. 17, various selectionmenus 1730, 1740, and 1750 and the like are displayed in a wish listscreen 1700 together with goods information 1710 and 1720 includingimages, names, and prices of goods. When one piece of goods informationis selected in FIG. 17, the controller 130 may displays detailedinformation for the selected goods.

When the user selects a shopping path menu 1740 in the screen asillustrated in FIG. 17, the controller 130 displays a path guide screen1800 configured to display locations of shops which sale the goodsregistered in the wish list on a map.

FIG. 18 illustrates an example of the path guide screen 1800. FIG. 18illustrates that two pieces of path guide information 1810 and 1820 fortwo goods are provided. When one of the two pieces of path guideinformation is selected, the selected information may be expanded anddisplayed.

As described above, the wallet application may provide various screensaccording to managing information. As in the exemplary embodimentsdescribed in FIGS. 1 and 2, when the wallet application is immediatelyexecuted by the user's gesture in a disabled state of the mobile device,an execution screen of the wallet application initially displayed may beone of the above-described various screens. That is, the payment homescreen 500 may be initially displayed or the card list screen 600 may beinitially displayed. Alternatively, the authorization screen for userauthorization may be initially displayed. FIG. 19 is a view explaining apayment process when the authorization screen is first displayed.

Referring to 19000 a, when a user operation in which the user touchestwo points T1 and T2 on a surface of the display unit 110 of the mobiledevice using two fingers and simultaneously moves two fingers outwardfrom the touched points, that is, interaction is performed, anauthorization screen 1910 as illustrated in 19000 b is displayed. Aninput region 1911 and a key pad region 1912 may be displayed in theauthorization screen 1910. When the user inputs a correct passcode, thecontroller 130 displays a card list screen 1920 as illustrated in 19000c. The card list screen 1920 illustrated in 19000 c is the same as thescreen of FIG. 7 and thus, repeated description thereof will be omitted.The user may perform tagging on the mobile device to a PoS terminal in astate in which the screen as illustrated in 19000 c is displayed. Inthis case, the representative card information 610 may be provided tothe PoS terminal by a NFC module provided in the communication unit 150.Therefore, the payment is done. On the other hand, when the user selectsan application execution termination button or when the user does notperform payment for a certain period of time, a notification message1930 as illustrated in 19000 d may be displayed. The user mayarbitrarily select menus 1931 and 1932 displayed in the notificationmessage 1930 and select whether or not the wallet application isterminated. When the wallet application is terminated, the controller130 converts the mobile device into a disabled state again. That is, thecontroller converts the mobile device into a lock state and causes thedisplay unit 110 to be off.

The wallet application has to be not executed in the disabled state bythe user operation. That is, when an icon for the wallet application isselected in a main screen or an icon display screen of the mobiledevice, the wallet application may be executed. FIG. 20 illustrates anoperation for this case.

As illustrated in 20000 a, various icons may be displayed in a mainscreen 2000. When an icon 2010 corresponding to the wallet applicationamong the icons is selected, an authorization screen 2020 is displayedas illustrated in 20000 b. When the user inputs a passcode using aninput region 2021 and a key pad 2022, a payment home screen 2030 isdisplayed as illustrated in 20000 c. The payment home screen 2030 hasbeen described in FIG. 5 and thus, repeated description thereof will beomitted. Like the example of FIG. 19, when the user select theapplication execution termination button in the payment home screen 2030or when the user does not perform an operation for a certain period oftime, a notification message 2040 as illustrated in 20000 d may bedisplayed. Various selection menus 2041 and 2042 may be displayed in thenotification message 2040. When the user selects a Yes menu 2041,execution of the wallet application is terminated and is restored to anoriginal state as illustrated in 20000 a. On the other hand, when theuser selects a No menu 2042, the screen as illustrated in 20000 c ismaintained.

The user may arbitrarily set an option with respect to an operation ofthe wallet application.

FIG. 21 illustrates an example of a setting screen for setting an optionof the wallet application. Referring to FIG. 21, a region 2110 forselecting a payment mode and a region for selecting an authorizationmethod may be displayed in a setting screen 2100.

The payment mode may include an automatic mode 2111 and a manual mode2112. The automatic mode 2111 may be a mode in which a payment isautomatically performed without a credit card and the manual mode 2112is a mode in which the credit card has to be selected before thepayment. Further, there are a PIN code 2121, a signature 2122, a patterninput 2133, and the like as the authorization method. The user mayselect a desired option to use the wallet application. Data set by theuser through the setting screen 2100 is stored in the storage unit 140.Therefore, the data may be used in the subsequent execution of thewallet application.

FIG. 22 is a flowchart specifically illustrating a payment methodaccording to another exemplary embodiment. Referring to FIG. 22, themobile device 100 may sense a user operation even in a screen off stateof the display unit 110 or a locked state of the display state 110(S2210). When the user operation is sensed, the mobile device determineswhether or not the sensed user operation is a preset gesture (S2215).When it is determined that the sensed user operation is the presetgesture, the mobile device immediately enables the display unit andautomatically executes the wallet application (S2220). Subsequently, themobile device displays set card information in an execution screen ofthe wallet application (S2240).

On the other hand, when it is determined that the sensed user operationis not the preset gesture but an operation for performing an unlockoperation (S2225), the mobile device performs an unlock operation(S2230) and displays a main screen. When a wallet application icon isselected in the main screen (S2235), the mobile device executes thewallet application (S2220) and display card information (S2240).

In this state, when the user performs tagging on an external apparatus(for example, a PoS terminal) (S2245), the mobile device determineswhether or not a transaction amount is small (S2250). A determinationcriterion amount may be determined according to a financial policy. Forexample, when the criterion amount is 300 thousand won, an amount ofbelow 300 thousand won may be determined as a small amount. When it isdetermined that the transaction amount is small, the mobile deviceimmediately perform the payment and displays payment completion. Thatis, in the first tagging process, the mobile device may check the amountand immediately transmit payment information. The transmitted paymentinformation may be card information displayed in the execution screen ofthe wallet application.

On the other hand, when it is determined that the transaction amount isnot small, the mobile device displays a PIN input screen (S2255). Amountinformation acquired from the external apparatus in the tagging processmay be also displayed in the displayed PIN input screen.

When the tagging operation is not performed in S2245 and a pay executionbutton is selected in the execution screen of the wallet application(S2260), a PIN input screen not including the payment amount isdisplayed (S2265).

When the PIN input is completed in the PIN input screen in S2255 orS2265 (S2270), the mobile device checks whether or not the input PIN isidentical with preregistered information (S2275). When it is determinedthat the input PIN is identical with the preregistered information, amessage which guides the user to perform tagging on the PoS terminal maybe displayed (SS2285). Thus, when the user performs the tagging on themobile device to the PoS (S2290), the payment is done and a paymentcompletion message is displayed (S2295). When it is determined that thePIN information is not identical with the preset information in S2275,the PIN input screen is displayed again (S2280). At this time, thenumber of errors may be also displayed and when the PIN input is failedmore than the predetermined number, the wallet application may beforcibly terminated.

Assuming that authorization is performed using the PIN and payment isperformed in an NFC manner in FIG. 22, the payment method has beendescribed. However, as described above, the authorization and paymentmethod is not limited thereto.

FIG. 23 is a view explaining a process of performing payment throughtagging with the PoS terminal. When the user input a predeterminedgesture in the mobile device 100 and then performs tagging on a PoSterminal 200 to the mobile device 100 as illustrated in 23000 a, anauthorization screen 2310 is displayed as illustrated in 23000 b. Whenthe user input a PIN in the authorization screen 2310 and then selects apayment menu 2311, a screen 2330 which guides PoS contact is displayedas illustrated in FIG. 23000c . Information for a payment option, animage of the PoS terminal, a guide phrase, a payment amount, and thelike may be displayed in the screen 2320.

Accordingly, tagging is performed again as illustrated in 23000 d, thepayment is done and an electronic receipt 2330 is issued and displayedas illustrated in 23000 e. A payment amount, a company, and a paymentdetail, and the like may be displayed in the electronic receipt 2330 anda menu 2331 for requesting to split the amount to other users, an OKmenu 2332, and the like may be displayed. When the OK menu is selectedin FIG. 23000e or when a preset critical period of time is elapsedwithout input, the screen is restored to the screen before the Posterminal contact.

FIG. 24 illustrates an example of an error message displayed when anincorrect passcode is entered. Referring to FIG. 24, an authorizationcancel menu 2411, a retry menu 2412, or the like may be furtherdisplayed in an error message 2410 in addition to the number ofincorrect input and a guide phrase. When the authorization cancel menu2411 is selected, the payment process may be terminated.

FIG. 25 illustrates an example of a payment completion message displayedwhen the payment is completed. When the payment is completed, anelectronic receipt as illustrated in 23000 e may be displayed or apayment completion message 2500 as illustrated in FIG. 25 may bedisplayed. A payment relevant simple guide phrase may be displayed inthe payment completion message 2500.

As described above, in the mobile device, the preset user operation isinput and the wallet application is immediately executed and used.According to other exemplary embodiments, the user's fingerprint may berecognized to reinforce security of the wallet application.

FIG. 26 illustrates a configuration of a mobile device according toanother exemplary embodiment. Referring to 26000 a, a mobile device 100may further include a fingerprint sensor 2600. The fingerprint sensor2600 may sense a user's fingerprint.

The controller 130 determines whether or not the fingerprint sensed inthe fingerprint sensor 2600 matches a user's preregistered fingerprint.Further, the controller 130 determines whether or not the user's touchoperation performed together with the sensing of the fingerprint matchesthe preset gesture information. When it is determined that the user'stouch operation matched with the gesture information and the user'sfingerprint matched with the preregistered fingerprint information aresensed, the controller 130 immediately enables the display unit 110 andexecute the wallet application.

26000 b illustrates that a gesture, in which the user inputs his/herfingerprint in the fingerprint sensor 2600 and at this state, the usermoves a finger 10 to a direction of the display unit 110 (that is, a Zdirection), is input. The controller 130 determines that the user'spredetermined operation is done when the touch is continuously done froma boundary of the display unit 110 above the fingerprint sensor 2600 toa fixed height within a certain period of time after the preregisteredfingerprint is recognized. According to this, the controller 130 enablesthe display unit 110 and automatically executes the wallet application.

FIG. 27 illustrates another example of a mobile device including afingerprint sensor. Referring to FIG. 27(a), a plurality of fingerprintunits 2710 and 2720 are disposed at both sides of a display unit 110.Each of the fingerprint sensors 2710 and 2720 has a thin bar shape.Thus, when two fingers of the user pass through the fingerprint sensors2710 and 2720, the fingerprint may be recognized.

27000 b illustrates that a gesture, in which two fingers touches twopoints on a surface of the display unit 110 and then moves to an X−direction and an X+ direction respectively and passes through thefingerprint sensors 2710 and 2720, is input. The fingerprint sensors2710 and 2720 sense the fingerprints when the user's fingers passthrough the fingerprint sensors 2710 and 2720 and provide sensedfingerprints to the controller 130. The controller 130 compares theprovided fingerprints and fingerprints stored in the storage unit 140.The controller 130 determines that an execution condition of the walletapplication is satisfied when a touch trajectory sensed in the sensor120 matches the preset gesture information and the fingerprints sensedin the fingerprint sensors 2710 and 2720 are matched with the registeredfingerprints.

The fingerprint recognition may be performed through various methods.Specifically, as the fingerprint recognition method, there are a methodusing a semiconductor chip and a method using an optical unit.

The method using a semiconductor chip is a method of sensing a shape ofa fingerprint using an electric conduction characteristic of a skin.That is, the method is a method of reading change in an amount ofcharges sensed by a sensor array and obtaining fingerprint informationaccording to pressure of the fingers placed on a chip surface of asilicon chip and a heat image when fingertips come in direct contactwith the surface of the silicon chip. The method using a semiconductorchip may be applied to the fingerprint sensors 2600 having the structureof FIG. 26.

The method using an optical unit is a method of emitting light,receiving the light reflected from a surface of a finger, and sensingcharacteristic of the finger surface.

FIG. 28 illustrates a fingerprint sensor implemented with the methodusing an optical unit. Referring to FIG. 28, the fingerprint sensorincludes a glass plate 2810, a light source 2820, a lens 2830, and alight-receiving unit 2840.

The light source 2820 emits light to the glass plate 2810 and thus thelight from a finger 10 placed on the glass plate 2810 is reflected. Thereflected light is incident to the light-receiving unit 2840 through thelens 2830. The light-receiving unit 2840 may include an image sensorsuch as a charge coupled device (CCD). The finger image sensed inlight-receiving unit 2840 may be analyzed and a fingerprint may berecognized. For clarity, FIG. 28 illustrates that the light source 2820and the light-receiving unit 2840 are spaced apart from the glass plate2810 to be tilted at a certain angle. However, a distance between thelight source 2820 and the glass plate 2810 and between thelight-receiving unit 2840 and the glass plate 2810 may be implemented tobe close according to a thickness of the mobile device 100. Further, thelight source 2820 and the light-receiving unit 2840 may be verticallydisposed below the glass plate 2810 with respect to the glass plate2810.

The number of fingerprint sensors and a size and arrangement location ofthe fingerprint sensor may be implemented in various structures otherthan structures illustrated in FIGS. 26 and 27.

FIG. 29 is a block diagram integrally explaining a configuration of amobile device according to various exemplary embodiments. Referring toFIG. 29, a mobile device 100 includes a global positioning system (GPS)chip 161, a digital multimedia broadcasting (DMB) receiver 162, a motionsensor 163, an audio processor 164, a video processor 165, a speaker166, a button 167, a capturing unit 168, and a microphone 169 inaddition to a display unit 110, a sensor 120, a controller 130, astorage unit 140, and a communication unit 150.

The controller 130 may control an overall operation of a user terminalapparatus using a program stored in the storage unit 140. Specifically,the controller may sense a user operation done on a surface of thedisplay unit 110. According to this, the controller may execute anapplication corresponding to the user operation. The wallet applicationmay be matched with a specific gesture as in the above-describedexemplary embodiments, but this is not limited thereto. For example,various applications such as a mail application or a call applicationmay be matched in addition to the wallet application. Further, only oneuser gesture does not have to be set. For example, a plurality of usergestures may be set and the user gestures may be matched withapplications different from each other.

The controller 130 may include a random access memory (RAM) 131, a readonly memory (ROM), a min central processing unit (CPU) 133, a graphicprocessing unit (GPU) 134, a bus 135, and the like. The RAM 131, ROM132, main CPU 133, GPU 134, and the like may be connected to each otherthrough the bus 135. Various interfaces may be further included, butillustration and description thereof will be omitted.

The main CPU 133 access to the storage unit 140 and performs bootingusing operating system (OS) stored in the storage unit 140. A commandset for system booting and the like may be stored in the ROM 132. When aturn-on command is input and power is supplied, the main CPU copies theOS stored in the storage unit 140 to the RAM 131 according to a commandstored in the ROM 132 and executes the OS to boot the system. When thebooting is completed, the main CPU 133 copies various types of programsstored in the storage unit 140 to the RAM 131 and executes the programscopied to the RAM 131 to perform various types of operations. When anapplication set to default exists, if the booting is completed, the mainCPU 133 may automatically execute the programs. The main CPU 133 maymonitor a sense signal output from the sensor 120 and determine whetheror not a wallet application is executed. When it is determined that anexecution condition of the wallet application is satisfied, the main CPU133 loads the wallet application from the storage unit 140 to the RAM131. The loaded wallet application controls respective components in themobile device 100 and performs operations according to theabove-described various exemplary embodiments.

The GPU 134 generates various types of screens. Specifically, the GPUmay perform rendering on a wallet screen based on information forvarious types of payment options stored in the stored in the storageunit 140 when the wallet application is executed.

The communication unit is configured to perform communication withvarious kinds of external apparatuses according to various types ofcommunication methods. The communication unit 150 includes a Wi-Fi chip151, a Bluetooth chip 152, a near field communication (NFC) chip 153, awireless communication chip 154, and the like.

Among the chips, the NFC chip 153 is a chip configured to perform NFCcommunication. The NFC is a non-contact short-range wirelesscommunication method using a frequency bandwidth of 13.56 MHz. When NFCtechnology is used, if a plurality of terminals approach each otherwithin a short range of about 10 cm, data may be transmitted andreceived. Tagging is performed to perform the short-range communication.The tagging is a behavior in which an apparatus including a NFC tag andany one of apparatuses including NFC readers approach each other towardthe counterpart and located within a communicable range in which the NFCmay be performed. The NFC chip 153 may include only NFC tag, but the NFCchip 153 may be implemented with one module in which the NFC tag and theNFC reader integrated.

The wireless communication chip 154 denotes a chip configured to performcommunication according to various communication standards such asInstitute of Electrical and Electronic Engineers (IEEE), Zigbee, thirdgeneration (3G), third generation partnership project (3RPP), and longterm evolution (LTE). The communication unit 150 may include at leastone among the above-described chips or chips according to othercommunication standards and perform communication with various externalapparatuses using the chips.

The GPS chip 161 is configured to receive a GPS signal from a GPSsatellite and calculate a current location of the mobile device 100.

The DMB receiver 162 is configured to receive and process a DMB signal.

The sensor 120 is configured to sense touch on a surface of the displayunit 110. The controller 130 may compares a coordinate value of eachobject displayed in a displayed screen and a touch coordinate value ofthe sensor 120 and determines whether which object is selected.

The motion sensor 163 is configured to sense a motion such as a rotationstate of the mobile device 100 using a gyro senor, a geomagnetic sensor,an acceleration sensor, and the like. The controller 130 may performvarious control operations according to a motion sensed by the motionsensor 163 in addition to a touch operation sensed by the sensor 120.

The audio processor 164 is configured to perform processing on audiodata included in contents. Various processing such as decoding andamplification for the audio data or noise filtering may be performed inthe audio processor 164.

The video processor 165 is configured to perform processing on videodata included in the contents. Various processing such as decoding forthe video data, scaling, noise filtering, frame rate conversion, andresolution conversion may be performed in the video processor 165.

The audio processor 164 and the video processor 165 may be driven when aprogram for reproducing contents received from an external source or thecontents stored in the storage unit 140 is executed.

The display unit 110 may display an image frame generated in the videoprocessor 165 as well as various screens on which the GPU 134 performedrendering. The speaker 166 output audio data generated in the audioprocessor 164.

The button 167 may be provided in a body of the mobile device 100 invarious types such as a home button, a push button, a touch button, or awheel button.

The capturing unit 168 is configured to perform a capturing operation.The controller 130 may select an image corresponding to an electronicreceipt among images captured in the capturing unit 168, attach theimage to the electronic receipt, and store the image-attached electronicreceipt in the storage unit 140.

The microphone 169 is configured to receive user's voice or other soundand convert the user's voice or the sound into audio data. Thecontroller 130 may use the user's voice input through the microphone 169in a call process or converts the user's voice into audio data andstores a conversion result.

The above-described exemplary embodiments has described that theapplication is automatically executed only by the touch gesture on thesurface of the display unit 110, but the application may beautomatically performed by other types of user operations. For example,the controller 130 may immediately execute a matched application eventhrough a motion gesture of a user recognized using the capturing unit168 or speech input through the microphone 169.

FIG. 29 integrally illustrates mountable various components when themobile device 100 integrally supports various functions such as acommunication function, a DMB function, and a GPS reception function.Therefore, in some embodiments, a portion of the components illustratedin FIG. 29 may be omitted or changed or other components may be furtheradded to the mobile device.

FIG. 30 illustrates an example of a software hierarchic structure of amobile device. Referring to FIG. 3, the mobile device 100 may includevarious software such as an OS 141, a frame work 142, a call application143, a wallet application 144, a browser 145, and a phone bookapplication 146 as well as a hardware 3000.

The hard ware 300 denotes various types of hardware illustrated in FIG,29. The OS 141 may control an overall operation of the hardware 3000 andmange functions of the hardware 3000. That is, the OS 141 is a hierarchywhich is in charge of a basic function such as hardware management,memory, and security. The OS 141 may drive a display driver configuredto drive the display unit 110, a communication driver configured toenable the communication unit 150 to transmit/receive signals, a cameradriver configured to drive the capturing unit, an audio driverconfigured to drive the audio processor 164, modules of a power managerand the like to control the operation of the mobile device 100.

The frame work hierarchy 142 exists in an upper hierarchy of the OS 141.The framework hierarchy 142 performs functions for connecting respectiveapplication programs 143 to 146 of an application hierarchy to the OShierarchy 141. For example, the frame work hierarchy 142 includes alocation manager, a notification manager, a frame buffer configured todisplay an image to the display unit, and the like.

The application hierarchy configured to implement various functionsexists in an upper hierarchy of the frame work hierarchy 142. The walletapplication 144 exists in the application hierarchy. The walletapplication 144 may provide various shopping services using variouspieces of information as illustrated in FIG. 3.

According to the above-described exemplary embodiments, shoppingservices may be used conveniently easily using a user terminalapparatus. In particular, the payment may be rapidly performed using thewallet application. In this disclosure, the application is called thewallet application, but the name of the application performing theabove-described operation may be variously determined. Further, theexemplary embodiments have described that the payment application isautomatically executed by a user gesture in a disabled state of thedisplay unit, but this is not limited thereto. That, even in an enablestate of the mobile device 100, when the predetermined user gesture isinput, the payment application may be executed.

The above-described payment methods according to the exemplaryembodiments may be implemented with a program which is performed throughvarious computer devices and then recorded in various non-transitorycomputer-readable media.

Specifically, the non-transitory computer-recordable medium, in whichthe program which provides the shopping service by sequentiallyperforming of sensing user's touch done on a surface of a display unitof a mobile device in a disabled state of the display unit of the mobiledevice; enabling the display unit when a user's touch operation matchedwith preset gesture information, executing a wallet application, anddisplay an execution screen; and transmitting information for a selectedpayment option to an external apparatus when the payment option isselected on the execution screen and performing a payment is recorded,may be mounted on the user terminal apparatus.

The non-transitory computer-recordable medium, in which a program whichimplements the methods of providing service according to theabove-described exemplary embodiments is recorded, may be mounted on ahost apparatus or a server.

The non-transitory computer-recordable medium may be connected to ormounted on the above-described various types of mobile devices andsupport to execute the methods in the corresponding devices.

The non-transitory computer-recordable medium is not a medium configuredto temporarily store data such as a register, a cache, a memory, and thelike but an apparatus-readable medium configured to semi-permanentlystore data. Specifically, the above-described applications or programsmay be stored and provided in the non-transitory computer-recordablemedium such as a compact disc (CD), a digital versatile disc (DVD), ahard disc (HD), a blu-ray disc, a USB, a memory card, a read only memory(ROM), and the like.

The foregoing exemplary embodiments and advantages are merely exemplaryand are not to be construed as limiting the present inventive concept.The exemplary embodiments can be readily applied to other types ofdevices. Also, the description of the exemplary embodiments is intendedto be illustrative, and not to limit the scope of the claims, and manyalternatives, modifications, and variations will be apparent to thoseskilled in the art.

What is claimed is:
 1. A mobile device comprising: a touch screen; amemory storing instructions; and a processor configured to execute theinstructions to at least: in response to receiving a touch input on thetouch screen, compare the received touch input with gesture informationstored in the mobile device; based on the received touch input matchingwith the gesture information, execute a payment applicationcorresponding to the received touch input and display an executionscreen of the payment application, wherein the execution screen of thepayment application includes information on a card for making a payment;and based on a request for making the payment being received while theexecution screen is displayed, transmit, to an external apparatus,information for making the payment while executing the paymentapplication on the touch screen.
 2. The mobile device as claimed inclaim 1, further comprising a fingerprint sensor configured to sense afingerprint, corresponding to the touch input, wherein the processor isconfigured to execute the payment application based on the touch inputmatching the gesture information and the sensed fingerprint matchingpredetermined fingerprint information.
 3. The mobile device as claimedin claim 1, wherein the received touch input is a single gesture inwhich a plurality of points are touched on the touch screen and move toincrease a distance therebetween.
 4. A payment method of a mobiledevice, the method comprising: in response to receiving a touch input ona touch screen of the mobile device, comparing the received touch inputwith gesture information stored in the mobile device; based on thereceived touch input matching with the gesture information, executing apayment application corresponding to the received touch input anddisplaying an execution screen of the payment application, wherein theexecution screen of the payment application includes information on acard for making a payment; and based on a request for making the paymentbeing received while the execution screen is displayed, transmitting, toan external apparatus, information for making the payment whileexecuting the payment application on the touch screen.
 5. The method asclaimed in claim 4, further comprising: sensing a fingerprintcorresponding to the touch input; and determining whether or not thesensed fingerprint matches predetermined fingerprint information,wherein the payment application is executed based on the received touchinput matching the gesture information and the sensed fingerprintmatching the predetermined fingerprint information.
 6. The method asclaimed in claim 4, wherein the touch input is a single gesture in whicha plurality of points are touched on the touch screen and move toincrease a distance therebetween.
 7. The mobile device of claim 1,wherein the touch input is a swiping gesture in which a plurality ofpoints are touched on the touch screen and a swiping motion is made toincrease a distance between the plurality of touched points.
 8. Themobile device of claim 1, wherein the touch input is a swiping gestureperformed by at least two fingers moving away from each other.
 9. Themobile device of claim 1, wherein the mobile device is a smartphone. 10.The mobile device of claim 1, wherein the stored gesture informationcomprises a particular gesture corresponding to executing twopredetermined actions comprising unlocking the mobile device andautomatically executing the payment application, wherein in response tothe particular gesture, the execution screen of the payment applicationis displayed directly after a lock screen is displayed.
 11. The mobiledevice of claim 1, wherein the stored gesture information comprises apredetermined gesture which is a command to execute two differentactions by the mobile device.
 12. The mobile device of claim 11, whereinthe two different actions comprise a first action which is one ofturning on the mobile device, waking up the mobile device, and unlockingthe mobile device and a second action which is loading and executing thepayment application, wherein, in response to the predetermined gesture,the mobile device directly transitions from a black screen of the mobiledevice to the execution screen of the payment application.
 13. Themobile device of claim 12, wherein the second action further comprisesdisplaying the execution screen of the payment application without anyinitial display of the payment application for a selection by a user.14. A non-transitory computer readable storage medium storing a programhaving a method, the method comprising: in response to receiving a touchinput on a touch screen of the mobile device, comparing the receivedtouch input with gesture information stored in the mobile device; basedon the received touch input matching with the gesture information,executing a payment application corresponding to the received touchinput and displaying an execution screen of the payment application,wherein the execution screen of the payment application includesinformation on a card for making a payment; and based on a request formaking the payment being received while the execution screen isdisplayed, transmitting, to an external apparatus, information formaking the payment while executing the payment application on the touchscreen.
 15. The mobile device of claim 1, wherein, in response to thereceived touch input matching with the gesture information, theprocessor is further configured to change the state of the mobile deviceinto an active state and control the touchscreen to display theexecution screen of the payment application without displaying a mainscreen on the touch screen.